Merged
Conversation
The scoped package must be published from apps/cli/release, but running npm publish at the repo root targets the private monorepo package. Add a short script that always rebuilds the release directory and publishes that target. Constraint: npm does not dispatch bare npm p to package scripts Rejected: Make the root package public | that would expose the monorepo tarball Confidence: high Scope-risk: narrow Directive: Keep publish shortcuts pointed at apps/cli/release, not repo root Tested: npm run publish:cli:dry-run Tested: git diff --check
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated by gx branch finish (PR flow).